Post

Replies

Boosts

Views

Activity

Reply to Does your Canvas in Xcode crash all the time due to AXRemoteElement-BackgroundFetch?
Same issue here. After analyzing the crash log in detail, I can confirm this is not related to our code or derived data cache. Root cause: Infinite recursion (10,915 levels deep) in -[AXElement customActions] inside AXRuntime.framework, triggered by UIAccessibilityHierarchyEncoder when PreviewShell tries to serialize the accessibility tree on the AXRemoteElement-BackgroundFetch dispatch queue. The thread stack overflows into the stack guard region, causing EXC_BAD_ACCESS (SIGBUS) / KERN_PROTECTION_FAILURE. Environment: macOS 26.5 beta (25F5042g) Xcode 26.4 (17E192) Confirmed workaround: Setting a physical iOS device as the preview destination works correctly. The bug is isolated to the simulator runtime — PreviewShell on device does not go through the affected AXRemoteElement path. I've already filed a feedback report with the full crash log attached. I'd encourage everyone affected to file their own report — the more Incident IDs Apple has, the faster this gets prioritized.
20h
Reply to Does your Canvas in Xcode crash all the time due to AXRemoteElement-BackgroundFetch?
Same issue here. After analyzing the crash log in detail, I can confirm this is not related to our code or derived data cache. Root cause: Infinite recursion (10,915 levels deep) in -[AXElement customActions] inside AXRuntime.framework, triggered by UIAccessibilityHierarchyEncoder when PreviewShell tries to serialize the accessibility tree on the AXRemoteElement-BackgroundFetch dispatch queue. The thread stack overflows into the stack guard region, causing EXC_BAD_ACCESS (SIGBUS) / KERN_PROTECTION_FAILURE. Environment: macOS 26.5 beta (25F5042g) Xcode 26.4 (17E192) Confirmed workaround: Setting a physical iOS device as the preview destination works correctly. The bug is isolated to the simulator runtime — PreviewShell on device does not go through the affected AXRemoteElement path. I've already filed a feedback report with the full crash log attached. I'd encourage everyone affected to file their own report — the more Incident IDs Apple has, the faster this gets prioritized.
Replies
Boosts
Views
Activity
20h